Methods and systems for facilitating trusted form processing

ABSTRACT

A method for facilitating trusted processing of multiple forms for use with a document banking system, comprising: receiving a selection of an Auto-fill option and a form from a computing device, an account holder selects the Auto-fill option, the form including fillable field(s); authenticating the account holder based on login credential(s), the account holder has a document banking account including documents within the banking system; searching a form template for the form in the banking system, the form template including at least one fillable field similar to the fillable fields of the form; extracting a value corresponding to the at least one fillable field, the value being extracted from the document(s) of the account holder; and filling the form by overlaying the extracted value on the fillable field(s) of the form, the filled form being displayed along with a status information for the fillable field(s) at the computing device.

TECHNICAL FIELD

The presently disclosed embodiments relate to document banking, and moreparticularly to methods and systems for facilitating trusted formprocessing.

BACKGROUND

Consumers are often required to submit a significant number of documentsto organizations for various reasons, such as for purchasing services,submitting applications, etc. These documents are not available in asingle central repository, and instead are typically in paper form or instored electronic repositories, such as consumers' email account(s).Some of the required documents may even be lost or unavailable.

In addition, filling out forms, such as online forms, can be a tediousprocess for users, especially when it requires filling out repetitiveinformation each time the user avails a service, not to mention spendingtime looking up information from various sources before entering theinformation onto the form. In an exemplary scenario, if a user wishes torequest two financial products from the same bank, e.g., a mortgage loanapplication and a credit card application, then the user would need tofill in two different forms, repeating certain information, such asname, address, account id, etc.

Additionally, the businesses would have their own internal workflows ofvalidating the information that is provided in the application form,thereby also increasing servicing time. Since the information providedby the user is not verified, service providers spend a considerableamount of time cross-verifying the form content with supportingdocuments provided by the user.

SUMMARY

Related art solutions permit the Auto-filling of relevant fieldsretrieved from documents submitted previously. Further, some related artsystems employ machine-learning techniques to automatically fill one ormore fields across a diverse array of web forms. The related art systemsdo not solve the problem set, and instead only provide a fractionsolution in each space independently. These solutions only usepreviously submitted information, and do not reflect a tightrelationship between the form requirements and the user information. Ifcached information is dated, then the user would have to re-type thefield content again, thereby making it least efficient and timeconsuming for the user. Other repository solutions as described inrelated concepts below, do not necessarily verify/authenticate thecontent that is used to fill the forms.

It may therefore be beneficial to provide a system that can reduce thetime the user spends on filling forms, while ensuring that theinformation provided is verified and correct. The businesses thereforealso do not have to rely on their back offices for determining theveracity of the form contents.

An embodiment of the present disclosure provides a method forfacilitating trusted processing of a plurality of forms for use with adocument banking system. The method includes receiving a selection of anAuto-fill option and at least one form from a computing device. Anaccount holder selects the Auto-fill option displayed on the computingdevice. Further, the at least one form includes one or more fillablefields. The method further includes authenticating the account holderbased on at least one login credential entered by the account holder atthe computing device. The account holder has at least one documentbanking account within the document banking system. The document bankingaccount includes at least one document associated with the accountholder. The method further includes searching for a form templatecorresponding to the at least one form in the document banking system.The form template includes at least one fillable field similar to theone or more fillable fields of the at least one form. Further, themethod includes extracting at least one value corresponding to the atleast one fillable field. The at least one value being extracted fromthe at least one document associated with the account holder. The methodalso includes automatically filling the at least one form by overlayingthe extracted at least one value on the one or more fillable fields ofthe at least one form. The filled at least one form being displayedalong with a status information for each of the one or more fillablefields at the computing device.

Another embodiment of the present disclosure provides a document bankingsystem for facilitating trusted processing of a number of forms. Thedocument banking system includes a storage repository configured tostore a number of documents associated with a number of document bankingaccounts. Each of the document banking accounts is associated with atleast one of a number of account holders and a number of service points.A number of verification partners may verify the documents. The documentbanking system further includes a transceiving module configured toreceive a selection of an Auto-fill option and at least one form from acomputing device. An account holder may select the Auto-fill optiondisplayed on the computing device. The at least one form includes one ormore fillable fields. The document banking system also includes anauthentication module is configured to authenticate the account holderbased on at least one login credential entered by the account holder atthe computing device. The account holder has at least one documentbanking account in the document banking system. The document bankingaccount includes at least one document associated with the accountholder. Further, the document banking system includes a trusted contentmanaging module configured to search for a form template correspondingto the at least one form in the storage repository. The form templatemay include at least one fillable field similar to the one or morefillable fields of the at least one form. The trusted content managingmodule is also configured to identify the at least one fillable field ofthe form template which need to be filled. The trusted content managingmodule is also configured to extract at least one value corresponding tothe at least one fillable field. The at least one value is extractedfrom the at least one document associated with the account holder.Further, the trusted content managing module is configured toautomatically fill the at least one form by overlaying the extracted atleast one value onto the one or more fillable fields of the at least oneform.

Yet another embodiment of the present disclosure provides a method forfacilitating trusted processing of a number of forms for use with adocument banking system. The method includes receiving a selection of an“Auto-fill” option and at least one form from a computing device,wherein an account holder selects the “Auto-fill” option displayed onthe computing device, the at least one form including one or morefillable fields. The method also includes authenticating the accountholder based on at least one login credential entered by the accountholder at the computing device. The account holder has at least onedocument banking account in the document banking system. The documentbanking account includes at least one document associated with theaccount holder. The method further includes searching for a formtemplate corresponding to the at least one form in the document bankingsystem. The form template includes at least one fillable field similarto the one or more fillable fields of the at least one form. The methodalso includes identifying the at least one fillable field of the formtemplate which needs to the filled. The method further includesextracting at least one value corresponding to the at least one fillablefield. The at least one value is extracted from the at least onedocument of the account holder. The at least one document being verifiedby at least one verification partner. Furthermore, the method includesautomatically filling the at least one form by overlaying the extractedat least one value on the one or more fillable fields of the at leastone form. The filled at least one form is displayed along with a statusinformation for each of the one or more fillable fields at the computingdevice. The status information being at least one of a rigid, verified,and un-verified. The method also includes allowing the account holder tointeract with the filled at least one form displayed at the computingdevice.

A further embodiment of the present disclosure provides a documentbanking system for facilitating trusted processing of a number of forms.The document banking system may include a storage repository configuredto store a number of documents associated with a number of documentbanking accounts. The document banking accounts are associated with anumber of account holders and a number of verification partners. Thedocument banking system also includes a transceiving module configuredto receive a selection of an Auto-fill option and at least one form froma computing device, wherein an account holder selects the Auto-filloption displayed on the computing device. The at least one form includesone or more fillable fields. The document banking system also comprisesan authentication module configured to authenticate the account holderbased on at least one login credential entered by the account holder atthe computing device. The account holder has at least one documentbanking account in the document banking system. The document bankingsystem may include at least one document associated with the accountholder. Further, the document banking system includes a trusted contentmanaging module configured to search for a form template correspondingto the at least one form in the storage repository. The form templateincludes at least one fillable field similar to the one or more fillablefields of the at least one form. The trusted content managing module isalso configured to identify the at least one fillable field of the formtemplate which need to be filled. The trusted content managing module isalso configured to extract at least one value corresponding to the atleast one fillable field. The at least one value is extracted from theat least one document associated with the account holder. The trustedcontent managing module is also configured to automatically fill theform template by overlaying the extracted at least one value on the oneor more fillable fields of the at least one form. The filled at leastone form is displayed along with a status information for each of theone or more fillable fields at the computing device. The statusinformation being at least one of a rigid, verified, and un-verified.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic illustrating an exemplary system in accordancewith an embodiment of the present disclosure.

FIG. 2 is a schematic illustrating another exemplary system, inaccordance with another embodiment of the present disclosure.

FIG. 3 is a schematic illustrating structural components of a documentbanking system, in accordance with an embodiment of the presentdisclosure.

FIGS. 4A-4B is a flowchart illustrating a method for facilitatingtrusted processing of a plurality of forms via a document bankingsystem, in accordance with an embodiment of the present disclosure.

FIG. 5 illustrates an exemplary form, in accordance with an embodimentof the present disclosure.

FIG. 6 illustrates an exemplary machine-readable form representation, inaccordance with another embodiment of the present disclosure.

FIGS. 7A-7C illustrates exemplary interfaces for Auto-filling a form, inaccordance with an embodiment of the present disclosure.

DETAILED DESCRIPTION

The following detailed description is made with reference to thefigures. Preferred embodiments are described to illustrate thedisclosure, not to limit its scope, which is defined by the claims.Those of ordinary skill in the art will recognize a number of equivalentvariations in the description that follows.

DEFINITIONS

Definitions of one or more terms that will be used in this disclosureare described below. The term, “document banking” refers to documentstorage as well as trusted document transactions between one or moreparties. The term “document” refers to any information such as a text, avideo, an audio, a fingerprint that can be embedded inside a paperdocument or an electronic document, etc. Some or all of the operationsof document banking are analogous to traditional banking, which storesand transacts money. The term “document transaction” refers to anyactivity related to documents performed in a document banking system.Examples of document transactions include, but are not limited to,opening a new document account, depositing a document in the documentaccount, verifying a document, sending one or more documents through agateway, sending a document periodically to a beneficiary, receiving adocument from the document account, deleting a document, updating anexisting document and adding an account holder to a list ofbeneficiaries to send documents to the account holder.

The term “transaction engine” refers to a device or a software modulewithin the document banking system that processes all documenttransactions. The transaction engine may execute predefined functionscorresponding to the one or more document transactions to process thecorresponding document transactions. The term “billing and paymentmodule” refers to a device or a software module within the documentbanking system to handle billing and payment activities. Similarly, theterm “logging module” refers to a device or a software module within thedocument banking system to log the result of each document transaction.

The term “account holder(s)” refers to any individual or entity thatmaintains a document account with a document banking system. The term“storage repository” refers to any storage space available at a documentbanking system to store documents. Each account holder is allocated apre-defined space within the storage repository, wherein the pre-definedspace is associated with the document account of the account holder. Thestorage repository also stores a “profile database (DB)” to storeinformation related to the account holders. Further, the storagerepository stores documents in a predefined format, such as PDF, DOC,JPEG, MPEG, etc. The term “secure data technologies (SDT) module” refersto a device or a software module within the document banking system thatsecures and authenticates the documents stored in the storagerepository.

As used herein, the term “verification partners” refers to individualsor organizations who have the authority to certify the veracity ofdocuments. The verification partners include public offices (e.g.,Passport and Immigration Office, Income Tax Department, Motor VehiclesDepartment), private offices (e.g., banks, hospitals, schools) as wellas other offices or officials (e.g., gazette officers and notarizationservices). As used herein, the term “verification module” is a device ora software module within the document banking system that managesverification related activities at the document banking system. Once adocument is verified, a “verified tag” is associated with the document.

The term “gateway” refers to a communication channel used by thirdparties to connect account holders with their respective documentaccounts with a document banking system. The term “token” refers to aunique identifier generated by third parties. In some cases, the term“token” refers to a unique identifier generated by the document bankingsystem and sent to an account holder to confirm an action (such asdeleting or modifying of a document) initiated by the account holder.

Further, a ‘document banking system’ may be a combination of software,hardware, firmware, or combination of these, for analyzing theconversation between different users or between a customer care agentand a number of customers. The document banking system is furtherintended to include or otherwise cover all software or computer programscapable of performing the various heretofore-disclosed processing offorms and documents, etc., for the disclosed purposes. For example,exemplary embodiments are intended to cover all software or computerprograms capable of enabling processors to implement the disclosedprocesses. Exemplary embodiments are also intended to cover any and allcurrently known, related art or later developed non-transitory recordingor storage mediums (such as a CD-ROM, DVD-ROM, hard drive, RAM, ROM,floppy disc, magnetic tape cassette, etc.) that record or store suchsoftware or computer programs. Exemplary embodiments are furtherintended to cover such software, computer programs, systems and/orprocesses provided through any other currently known, related art, orlater developed medium (such as transitory mediums, carrier waves,etc.), usable for implementing the exemplary operations disclosed below.

In accordance with the exemplary embodiments, the disclosed computerprograms can be executed in many exemplary ways, such as an applicationthat is resident in the memory of a device or as a hosted applicationthat is being executed on a server and communicating with the deviceapplication or browser via a number of standard protocols, such asTCP/IP, HTTP, XML, SOAP, REST, JSON and other sufficient protocols. Thedisclosed computer programs can be written in exemplary programminglanguages that execute from memory on the device or from a hostedserver, such as BASIC, COBOL, C, C++, Java, Pascal, or scriptinglanguages such as JavaScript, Python, Ruby, PHP, Perl or othersufficient programming languages.

Some of the disclosed embodiments include or otherwise involve datatransfer over a network, such as communicating various inputs over thenetwork. The network may include, for example, one or more of theInternet, Wide Area Networks (WANs), Local Area Networks (LANs), analogor digital wired and wireless telephone networks (e.g., a PSTN,Integrated Services Digital Network (ISDN), a cellular network, andDigital Subscriber Line (xDSL)), radio, television, cable, satellite,and/or any other delivery or tunneling mechanism for carrying data.Network may include multiple networks or subnetworks, each of which mayinclude, for example, a wired or wireless data pathway. The network mayinclude a circuit-switched voice network, a packet-switched datanetwork, or any other network able to carry electronic communications.For example, the network may include networks based on the Internetprotocol (IP) or asynchronous transfer mode (ATM), and may support voiceusing, for example, VoIP, Voice-over-ATM, or other comparable protocolsused for voice data communications. In one implementation, the networkincludes a cellular telephone network configured to enable exchange oftext or SMS messages.

Examples of a network include, but are not limited to, a personal areanetwork (PAN), a storage area network (SAN), a home area network (HAN),a campus area network (CAN), a local area network (LAN), a wide areanetwork (WAN), a metropolitan area network (MAN), a virtual privatenetwork (VPN), an enterprise private network (EPN), Internet, a globalarea network (GAN), and so forth.

The computing devices are intended to include or otherwise cover allsoftware or computer programs capable of performing the variousheretofore-disclosed determinations, calculations, processing, etc., forthe disclosed purposes. For example, exemplary embodiments are intendedto cover all software or computer programs capable of enablingprocessors to implement the disclosed processes.

Overview:

Some disclosed embodiments generally relate to auto form filling withtrusted content via a document banking system. To this end, thedisclosure provides a document banking system that includes a repositoryfor storing account holders' documents (e.g., passport, driver'slicense, photos and/or videos or others) in a document account, andenables account holders to transact or transfer these documents to otheraccounts as and/or when requested for requesting or availing one or moreservices. For example, an account holder can efficiently send herdocument(s) from her document account to an intended recipient'sdocument account or to a service point's document banking account, e.g.,a bank, a hotel, a college, and so forth. Further, the disclosedembodiments allow the account holders to auto fill one or more formsusing the information or content of the pre-stored documents.

Auto filing of the forms involve authenticating the identities of theaccount holders, and filling the forms using the already verifiedinformation present in the pre-stored documents. This enhances orensures integrity as well as non-repudiation in sending or receiving ofdocument(s) across, between, or among the concerned parties. Thus, someof the disclosed embodiments relate to a method that allows automaticprocessing of form(s) using trusted and verified content or informationfrom various verified documents stored in a document banking system. Thedisclosed systems and methods provides convenient and secure way foraccount holders to auto fill forms, while providing the form-processingbusiness end with verified and trusted information.

An aspect of the disclosed system envisions a future state where anysupporting document submission for verification, is eliminated in anyform submission process. The document banking system stores andmaintains verified and authentic documents of the account holders. Oneor more verification partners may verify the documents when the accountholders upload them. In the document banking system, the contents ofsuch documents are verified at the source via an API or manually. Oncethe contents are deemed authentic, the document banking may label thedeposited documents and its contents as verified. Further, the contentsmay be stored in a key-value store with appropriate tags, etc. Thedisclosed systems and methods uses these documents for filling theforms. Hence there may not be any further requirement for verificationusing attached supporting documents and manning a whole back office forthe same.

Some embodiments of the present disclosure allows the account holder toopen an application form to apply for a service at a computing device.The account holder may click on an “Auto-fill” option displayed alongwith the form. The account holder may be prompted for entering logincredential (a) for accessing a document banking system. The documentbanking system may confirm the identity of the account holder based onthe login credential(s).

The disclosed systems are configured to capture a machine-readablerepresentation of the form and store it as a form template. The systemis also configured to extract all the fields for which values areneeded. One or more values for the extracted fields are determined frompre-stored documents in the document banking system. The documents areverified at the time of uploading by at least one verification partner.The form is then filled by overlaying the extracted one or more valueson one or more fillable fields of the form. Further, one or more statusinformation in form of markers may be displayed to the account holder.

Exemplary Embodiments

FIG. 1 is a schematic that illustrates an exemplary system 100, inaccordance with an embodiment of the present disclosure. The system 100includes a document banking system 106, which facilitates documenttransactions among various account holders registered with the documentbanking system 106. In an embodiment, the document banking system 106 ishosted on a server. The document banking system 106 may be software,hardware, firmware, or combination of these. In an embodiment, thedocument banking system 106 may be hosted on more than one server in anetwork. The architecture of the document banking system 106 isexplained in further detail in conjunction with FIG. 3 below.

The system also includes at least one account holder 102 configured tointeract with the document banking system 106. The account holder 102may communicate with the document banking system 106 by sending orreceiving one or more messages using a computing device 104. Thecomputing device 104 can be any suitable device capable of exchangingdata/messages over the network such as the Internet. Examples of thecomputing device 104 may include, but are not limited to, a desktopcomputer, a mobile phone, a tablet computer, a laptop, a personaldigital assistant (PDA), a smart phone, and so forth. One or moreindividuals such as the account holder 102, and one or morebusiness(es)/organization(s) such as a number of service points 116, mayhave document accounts with the document banking system 106. The accountholder 102 and the service points 116 may access their respectivedocument banking account by entering their specific login credentialsuch as a user id, an account number, a password, etc. The accountholder 102 may upload or download one or more documents to or from thedocument banking system 106. Examples of the one or more documents mayinclude, but are not limited to, social security number (SSN), PAN,birth certificate, mark sheets, driving license, academic degrees,certificates, medical reports, and so forth.

The at least one account holder 102 and the service points 116 mayregister with the document banking system 106 and create a documentaccount within the document banking system 106. After registration, theat least one account holder 102 and the service points 116 may upload ordownload documents to or from their respective account. Alternatively,the at least one account holder 102 and the service points 116 maydownload documents from a third party's account. The document bankingsystem 106 may also provide a storage to all its registered accountholders such as the at least one account holder 102 and the servicepoints 116.

Further, the at least one account holder 102 of the document bankingsystem 106 may interact with the document banking system 106 to performvarious types of document transactions. Various example of documenttransactions may include, but are not limited to, opening a new documentaccount, depositing a document in the document account, requesting aservice, searching for a service, verifying a document, sending adocument through a gateway, sending a document periodically to abeneficiary, receiving a document from the document account, deleting adocument, updating an existing document, adding an account holder tolist of beneficiaries to send documents to the account holder, etc.

As shown, the service points 116 capable of providing one or moreservices to the at least one account holder 102. Examples of the servicepoints 116 may include, but are not limited to, banks, hotels,hospitals, schools, colleges, passport offices, and so forth. Theservices may be one or more services directly or indirectly provided tothe account holder 102 by the service points 116. For example, a bankmay provide services such as, opening a bank account, applying for aloan, demat service, and so forth.

A given document transaction may be any known, related art, or laterdeveloped form, such as in any one of the following forms:Consumer-To-Business (C2B), Business-To-Consumer (B2C),Consumer-To-Consumer (C2C) and Business-To-Business (B2B). An example ofa C2B document transaction is an individual sending her resume to acompany in order to apply for a job. An example of a B2C documenttransaction is a company sending a job offer to a job applicant. Anexample of a C2C document transaction is a house owner sending a leaseagreement to the tenant. An example of a B2B document transaction is acompany sending financial documents to a bank for applying for a loan.The document transactions as described here are exemplary in nature andare not intended to limit the scope of the disclosure.

The document banking system stores and maintains the documents ofvarious account holders, such as the account holder 102, in theirrespective document banking account. The document banking system 106 maycommunicate with at least one verification partner 108 to verifydocuments stored in the document banking system 106. The verificationpartner(s) 108 includes public offices 110, private offices 112 as wellas other offices or officials 114. The document banking system 106establishes interactions with the at least one verification partner 108,either via a web-based API or manually, thereby enabling verification ofany given account holder's documents.

Further, the account holder 102 may communicate or interact with thedocument banking system 106 via one or more means as shown in a system200 in FIG. 2. For example, the account holder 102 may access the one ormore functionality or facilities of the document banking system byvisiting a document banking branch 202. In an exemplary scenario, theaccount holder 102 may access the document banking system 106 via acomputing device 204. In another exemplary scenario, the account holder102 may access the document banking system 106 via a document bankingATM 206 associated with the document banking system 106.

FIG. 3 illustrates various system elements of the document bankingsystem 106, according to an embodiment of the present disclosure. Thedocument banking system 106 includes a storage repository 302, a profileDataBase (DB) 304, a Secure Document or data Technologies (SDT) module306, a document transaction engine 308, a billing and payment module310, a verification module 312, a transceiving module 314, a servicepoint managing module 316, a location managing module 318, a displaymodule 320, an authentication module 322, and a trusted content managingmodule 324. These modules interact with each other to perform andaccomplish a desired task.

The transceiving module 314 is configured to allow exchange of data orinformation between the document banking system and the computing device104. The account holder 102 and the service points 116 may register withthe document banking system 106 and open a document banking account viaa registration module (not shown). Post registration the account holder102 may upload or download one or more documents to and from theirrespective document banking account with the document banking system106. The storage repository 302 may store a number of documentsassociated with a number of document banking accounts. In an embodiment,the storage repository 302 may store the documents of the at least oneaccount holder 102 (or the service points 116) in a reliable and securemanner using one or more known, related art or later developedtechnologies. For example, the storage repository 302 may allow accessonly through a firewall to enhance or ensure secure access. Further, thestorage repository 302 may employ anti-spyware and anti-virus programsto enhance or ensure data integrity and security.

The storage repository 302 may further store one or more formsassociated with one or more services. Each of the one or more forms mayinclude one or more fillable fields. The service points 116 may providethe services. The storage repository 302 may also store a number ofmachine-readable form templates corresponding to the one or more forms.Further, the storage repository 302 may store the templates ofwell-known documents i.e. passport, election ID, PAN card, etc. Theservice points 116 may register their forms template with the documentbanking system 106. Registration of document/form template is a one-timeexercise and all the users such as the account holder 102 and theservice points 116 can use these later.

Further, as shown, the trusted content managing module 324 is configuredto extract or generate a number of machine-readable form templatescorresponding to a number of forms stored in the storage repository 302.The forms may be associated with one or more services provided by theservice points 116. Further, the at least one form and the form templateis associated with at least one service provided by at least one servicepoint of the service points 116. The at least one service points isregistered with the document banking system 106 and has at least onedocument banking account with the document banking system 106.

In some embodiments, the trusted content managing module 324 may captureor identify an FDL representation of the at least one form which needsto be filled (e.g., the PAN application form) and may extract all thefields for which values are needed (say K). In some embodiments, thetrusted content managing module 324 is configured to search for a formtemplate corresponding to the at least one form in the storagerepository 302. The form template may include at least one fillablefield similar to the one or more fillable fields of the at least oneform.

The account holder 102 may fill the forms via the form templates foravailing one or more services as provided by the service points 116. Theservice points 116 for which the forms can be filled may register theform templates with the document banking system 106. For instance, theIndia income tax department, as a service point registered in thedocument banking system 106 may register the FDL (form definitionlanguage) representation of PAN (tax ID) application form in documentbanking system. The FDL representation (or machine-readable formtemplate) of PAN application then may be visible to all document bankingusers such as the account holder 102. It should be appreciated, that theterm “FDL representation” and the “form template” are used throughoutthis disclosure interchangeably without changing its meaning. Further,the application form in this way may be now document banking trustedAuto-fill enabled, i.e. along this form (PAN application form), an“Auto-fill” option may be available for this form to be Auto-filledusing the verified content or information or the pre-stored documents.

Further, structure of the form templates may be learned using one ormore known, related art or later developed technologies. In anembodiment, the trusted content managing module 324 is configured tolearn a structure of the form and generate a machine-readable formtemplate corresponding to the form. In an exemplary scenario, thetrusted content managing module 324 may generate an XML file thatcaptures all the details about the form. Any suitable language such as,but not limited to, a form definition language (FDL), an XML schema formdefinition language (FDL), may be used to generate the form templatesand to identify various formats of the various documents from which datais extracted as well as the new forms that need to be filled.

The trusted content managing module 324 is further configured to extractand store the content from the documents uploaded by the account holder102 or the service points 116. The trusted content managing module 324is configured to identify the at least one fillable fields of the formtemplate for which values need to be filled.

Further, the trusted content managing module 324 is configured toextract at least one value corresponding to the at least one fillablefields. The at least one value may be extracted from the at least onedocument associated with the account holder 102. In an embodiment, thetrusted content managing module 324 checks post uploading of a document,such as the passport, whether the uploaded document follows a knowntemplate or not. If yes, then the trusted content managing module 324may perform selective optical content recognition (OCR) on specificportions of the document to extract the text corresponding to the fieldsassociated with that portion of the document. In an embodiment, an OCRengine (not shown) may perform the selective optical contentrecognition. Further, the content extracted by the OCR engine maycontain lot of un-necessary information. The trusted content managingmodule 324 may try to extract meaningful content, using one or moreinformation retrieval techniques as well as document heuristics. In anembodiment, the meaningful information may be stored as one or more setsof entity-value pairs. The entity may represent a field as mentioned ina document or form and the value may refer to the value corresponding tothat field in the stored document/form. For example, “Name” is an entityand “David” is a value for the entity “Name”. In an embodiment, thestorage repository 302 stores multiple values corresponding to anentity. Further, the trusted content managing module 324 may update theentity-value pairs stored in the storage repository 302 with newentity-value pairs from the document. This means, there is a new valuefor an existing entity, the previous value of the entity is updated withthe new value in the storage repository 302.

Example of a PAN application form is mentioned for description purposeonly, the disclosed methods and systems may be implemented and used forany kind of form. The form includes a number of fillable fields (hereinafter referred as fields). Further, the account holder 102 may click orselect the Auto-fill option on the PAN application form (or at least oneform). The authentication module 322 may prompt the account holder 102to enter one or more login credential for validating the identity of theaccount holder 102 and his/her document banking account. Examples of thelogin credential may include a name, password, a user identity (ID),account number, and so forth. The login credential may be received bythe transceiving module 314 of the document banking system from thecomputing device 104. The authentication module 322 may validate orauthenticate an identity of the account holder 102 (or associateddocument banking account) based on the received login credential.

The trusted content managing module 324 may determine a match for theextracted fields (such as K fields) from the stored entity-value pairsin the storage repository 302. In some cases, simple pattern matchingmay be done for determining the match. However, in some other cases, thesimple pattern matching may not work because different documents/formscan use different names for the same field or entity. For examples, DoBand Date of birth for same entity (or field) may be used in differentdocuments or forms. The trusted content managing module 324 may utilizevarious available dictionaries and domain knowledge along withtechnologies such as Natural Language Processing (NLP), and MachineLearning (ML) to identify highly accurate entity value matches for theextracted fields. Further, if there is more than one value for anentity/field in the storage repository 302 then the display module 320may display multiple values to the account holder 102 for selection.Further, each field may be associated or assigned with a marker or tagbased on a status information. The status information may define a typeof the value for the field. The type of the value (or content of thefields) or the status information may be such as, not limited to, rigid,verified, un-verified, and so forth. Further, the tag or marker may bedisplayed using a specific color, for example, the rigid content may bedisplayed using a red color, verified content/value may be displayedusing a green color, and un-verified content/value may be displayedusing a yellow color. In another embodiment, one or more symbols may beused along with the value to define the status information for thedifferent fields. For example, “√” for verified content/value and “x”for un-verified content. Further, in an embodiment, the rigidcontent/value cannot be altered.

The rigid content is from the profile of the account holder 102. When adocument banking account is opened, as in any bank account, the accountholder's authenticity is verified. Thus, the profile stores informationabout the account holder 102. Certain parts of the information may beconsidered rigid, as they cannot be changed without KYC(Know-Your-Customer) norms revisit. Examples of the rigid content mayinclude, but are not limited to, First name, Middle name/initial, Lastname, Date of Birth, Social Security Number (SSN), and so forth. Due tothe KYC the document banking system 106 may itself verify all thesedata. The account holder 102 may not be able to change or alter therigid content on his/her own.

The verified content refers to the content extracted from verifieddocuments. During the deposit of a document, the account holder 102 mayrequest the authenticity of the document deposited be verified by thedocument banking system 106. The document may be verified by theverification partner(s) 108. If the document is verified as authentic bythe issuer or the verification partner 108 of the document, then thecontent extracted from the verified document is classified as verifiedcontent. The document/content may be generated by an organization or aservice point of the service points 116, which is registered with thedocument banking system 106 and its authenticity is verified,independent of the account holder 102. Further, the account holder 102may not be able to change the verified content on his/her own. Exampleof the verified content may include, but not limited to, Passportnumber, PAN, SSN, and so forth. The un-verified content may include thecontent/value, which is extracted from the documents in the documentbanking account that are not verified or was not directly deposited bythe registered organizations or service points 116.

The trusted content managing module 324 may be configured to fill theform template by overlaying the extracted at least one value on the atleast one fillable fields of the at least one form (e.g., PANapplication form). The filled at least one form, i.e., the filled PANform, may be displayed along with a status information at the computingdevice 104. The status information is shown by marking the value of thefield using a specific color or using one or more symbols. The statusinformation shows the type of the value such as rigid content, verifiedcontent, or un-verified content.

The display module 320 is configured to display the filled at least oneform and the status information of each of the one or more fields at thecomputing device 104. The account holder 102 may then interact with thedisplayed filled form (i.e., filled PAN application form). The displaymodule 320 may display a marker or tag for each of the field value camefrom the Auto-fill process to represent if that field value came from atleast one of a rigid, verified, or un-verified content. The displaymodule 320 is configured to provide an interface at the computing device104 to allow the account holder to interact with the filled at least oneform. Further, the account holder 102 may accept, reject or edit thesedisplayed values based on one or more rules as described in detail withreference to FIG. 7C.

The trusted content managing module 324 is further configured to allowthe service points 116 to register their document templates along withcustomized rules for template usage. The trusted content managing module324 is also configured to perform OCR on selected content of one or moreforms. Further, the trusted content managing module 324 is configured toextract and create entity-value pairs used for auto filling the one ormore forms as per requests received from the account holder 102.Further, the trusted content managing module 324 is configured to offersecure application programming interfaces (APIs) for the service points116 to connect to the document banking system 106 and extract accountholder related information from the storage repository 302. Furthermore,the trusted content managing module 324 is configured to auto fill formsby overlaying content on the pre-registered form templates stored in thestorage repository 302.

The trusted content managing module 324 is configured to transfer thefilled at least one form in the at least one document banking account ofat least one service point based on one or more pre-defined rulesdefined by the service points 116. Further, the filled at least one formtemplate is transferred to the at least one document banking account ofthe at least one service point of the service points 116 when theaccount holder 102 provides submit instruction at the computing device104. In some embodiments, the filled at least one form is stored in thestorage repository 302.

As shown, the profile DB 304 may store account information of the atleast one account holder 102; for example, login credentials,beneficiary list and other related information. The SDT module 306 helpsin authenticating the documents and storing the documents in apre-defined format in the storage repository 302. The SDT module 306 mayuse one or more known, related art or later developed technologies, forexample, encryption, to authenticate documents and store them in anencrypted form. The document authentication ensures that documentscannot be modified inadvertently or reduces such inadvertentmodification.

The service point managing module 316 may maintain information about theservice points 116 along with one or more services that the servicepoints 116 may provide. In some embodiments, the service point managingmodule 316 may maintain the information using the DocR-tree datastructure. The service points 116 are the registered account holderswith the document banking system 106. The service point managing module316 may also store information about spatial locations on a map of theservice points 116. Further, the registration of a new service point oraddition of a new service by an existing registered service point may beprovided via the service point managing module 316.

The location managing module 318 maintains information about respectivelocation of the at least one account holder with a given region-basedgranularity. The location managing module 318 may keep track of therespective locations of the account holder 102. For example, thegranularity of the region may be 50 meters by 50 meters, or 1 Km by 1Km, and so on. The optimal granularity to be used may depend essentiallyupon spatial density of the region. Further, the location managingmodule 318 may keep track of the locations or movements of only thoseusers or account holders who have subscribed to this service andlaunched the document banking application on their device. Hence,whenever the account holder 102 launches the document bankingapplication on his/her device, a trigger may be generated for thelocation managing module 318 and it may start tracking the movements ofthe account holder 102. The tracking may end once the account holdercloses the document banking application on the device.

The at least one account holder 102 may access the document bankingsystem 106 via a document banking application running at an associateddevice or via entering a universal resource locator (URL) in a browsingapplication at the device. The document banking application may be aninterface for allowing the at least one account holder 102 to access thedocument banking system 106. When the document banking application is onat the device, then the location managing module 318 keeps on trackingthe location of the at least one account holder 102 in real time. Thelocation managing module 318 may stop tracking the location of the atleast one account holder 102 when the document banking application isclosed on the device.

The document transaction engine 308 may facilitate one or more documenttransactions among various parties including the at least one accountholder 102, the service points 116, the at least one verificationpartner 108, third parties, etc. The transaction engine 308 may alsoprocess the received at least one service request. The transactionengine 308 may also identify at least one service point from themultiple service point based on the at least one service request and/orthe respective location of the at least one account holder 102. The atleast one of the service points 116 is capable of providing the servicerequested in the service request. The transaction engine 308 may alsoadd at least one document required for processing the service request ina document transfer queue of the at least one of the service points 116.The document transaction engine 308 may also generate and provide areference number to the at least one account holder 102. Further, basedon one or more rules or predefined conditions as specified by the atleast one of the service points, the transaction engine may transfer theat least one document to an account of the at least one of the servicepoints 116. The transfer of the at least one document may be initiatedbased on the rules. Further, the transaction engine 308 may manage andsupervise the at least one document transaction occurring in the mobilesettings of a mobile device, for example.

Further, the display module 320 may display content or information tothe user. For example, the display module 320 may display the at leastone of the service points 116 along with the associated services andother information including one or more service options to the at leastone account holder 102. The service options may be an option to allowthe at least one account holder 102 to download a copy of the documents,or to add the documents to a document transfer queue of the at least oneof the service points 116. The display module 320 is also configured todisplay the filled forms and form templates to the account holder 102.

In some scenarios, the at least one account holder 102 may need to visita branch office of the at least one of the service points 116 forfurther verification. The documents may only be transferred from thedocument transfer queue to the document banking account of the at leastone of the service points 116 after verification.

The billing and payment module 310 handles billing related activitiesassociated with the one or more document transactions. When or ifrequested, the verification module 312 performs verification of thedocuments, either manually or via a web-based API. The verificationmodule 312 may verify the uploaded document with the help of variousverification partner(s) 108 as shown in FIG. 1.

The document banking system 106 may also include a notification module(not shown) to notify the at least one account holder 102 of accountactivity related to one or more document transactions. Moreover, thedocument banking system 106 includes a logging module (not shown) to loginformation related to all activities performed on the document bankingsystem 106. The logged information may be used to perform systemperformance analytics to facilitate reasonable document transactionresponse times as well as system scalability with respect to a largeand/or growing number of account holders and an increasingly largenumber of transactions. The statistics obtained by the performanceanalytics may include average time taken for different types oftransactions, most frequently requested transactions, etc. The obtainedstatistics may be available to the document banking system 106 so thatit may take corrective actions to maintain reasonable systemperformance. In some embodiments, the document banking system 106 mayalso include a scanner to scan documents and a printer to printdocuments.

In an exemplary embodiment, the at least one account holder 102 logsinto the document banking system 106. The document banking system 106uses the profile DB 304 to verify the login credentials of the at leastone account holder 102 before the at least one account holder 102 isallowed to access the document account at the document banking system106. Thereafter, the at least one account holder 102 initiates adocument transaction, such as a deposit document transaction, and sendsa document to the document transaction engine 308. The documenttransaction engine 308 processes the deposit document transaction as perthe predefined functionality. Thereafter, the SDT module 306authenticates the document sent by the at least one account holder 102and stores an encrypted copy of the document in the storage repository302. In some embodiments, the billing and payment module 310 updatesbilling information for the at least one account holder 102 based on thetype of the document transaction.

In cases where the at least one account holder 102 initiates a requestfor verifying a document, the verification module 312 identifies arelevant verification partner, in the at least one verification partner108, to verify the document. If successfully verified, the verificationmodule 312 sets a “verified tag” associated with the document to “TRUE”.Finally, the billing and payment module 310 updates billing informationfor the at least one account holder 102 based on the verified documenttransaction.

FIGS. 4A-4B is a flowchart illustrating a method for facilitatingtrusted processing of a plurality of forms via a document bankingsystem, in accordance with an embodiment of the present disclosure. Asdiscussed with reference to FIGS. 1-3. The account holder 102 is aregistered user of the document banking system 106. The computing device104 is configured to communicate with the document banking system 106.The service may be provided by the at least one of the service points116 which is also registered with the document banking system 106. Theaccount holder 102 may open a form for availing one or more service atthe computing device 104. The form is a registered form. An “Auto-fill”option is also displayed along with the form at the computing device 104of the account holder 102.

At step 402, at least one form along with an Auto-fill option isdisplayed on the computing device 104 based on a form selection receivedfrom the account holder 102. The at least one form may be an applicationform for applying for a service such as loan. The account holder 102 mayselect the Auto-fill option displayed on the computing device 104. In anembodiment, the display module 320 displays the form and the Auto-filloption at the computing device 104. At step 404, the at least one formand the selection of the Auto-fill option is received at the documentbanking system 106. In an embodiment, the transceiving module 314receives the form and the selection of the Auto-fill option from thecomputing device 104. The account holder 102 at the computing device 104may be prompted to enter at least one login credential to allow accessto the document banking system 106.

At step 406, the at least one login credential is received from thecomputing device 104. Examples of the login credential may include, butnot limited to, a user name, a user ID, a password, an account ID, anaccount number, and so forth. The transceiving module 314 may receivethe at least one login credential from the computing device 104. Then atstep 408, account holder 102 is authenticated based on the received atleast one login credential. In an embodiment, the authentication module322 may authenticate and validate an identity of the account holder 102(or of the document banking account associated with the account holder102).

At step 410, a form template corresponding to the at least one form issearched at the document banking system 106. The form template includesat least one field similar to the one or more fields of the at least oneform. As discussed with reference to FIG. 2, the storage repository 302stores a number of documents, forms, and form templates. The trustedcontent managing module 324 may search for the form templatecorresponding to the at least one form in the storage repository 302.Then at step 412, at least one field is identified from the formtemplate for which the value is required. In some embodiments, thetrusted content managing module 324 identifies the at least one fieldfrom the form template.

Thereafter at step 414, at least one value for the at least one field isextracted from at least one document associated with the account holder102. The trusted content managing module 324 may identify the at leastone document from the storage repository 302. The trusted contentmanaging module 324 may then extract at least one value for the at leastone field from the identified at least one document. In someembodiments, more than one value for the at least one fields isextracted. Then at step 416, the at least one form is filledautomatically by overlaying the extracted at least one value on the oneor more fillable fields of the at least one form. In some embodiments,the trusted content managing module 324 automatically fills the at leastone form. Further at step 418, the filled at least one form along with astatus information for each of the one or more fields is displayed atthe computing device 104. In some embodiments, the display module 320displays the filled at least one form at the computing device 104. Thestatus information may define the type of the content or value for eachof the one or more fields. For example, the value may be rigid,verified, and un-verified. The account holder 102 is allowed to interactwith the displayed filled at least one form. The account holder 102 mayselect or reject the values filled for the one or more fields. When theaccount holder is done with the selection or rejection of the form, theaccount holder 102 may choose to submit the filled at least one form. Atstep 420, based on the submission instruction from the account holder102, the filled at least one form is transferred in a document bankingaccount of at least one service point of the service points 116. In someembodiments, the action to be taken post receiving the submissioninstruction from the account holder is governed by or based on one ormore rules defined by the at least one service point. For example, onsubmission, the filled at least one form may be transferred in thedocument banking account of the at least one of the service points 116or may be transferred to the storage repository 302.

FIG. 5 illustrates an exemplary form 500, in accordance with anembodiment of the present disclosure. As shown, the form 500 may includea number of fillable fields. Examples of the one or more fillable fieldsmay include, but are not limited to, first name, last name, phonenumber, date of birth, and so forth.

FIG. 6 illustrates an exemplary machine-readable form representation ora form template 600, in accordance with another embodiment of thepresent disclosure. The account holder 102 may fill the forms via theform templates such as the form template 600 for availing one or moreservices that may be provided by the service points 116. The servicepoints 116 for which the forms can be filled may register the formtemplates with the document banking system 106. For instance, the Indiaincome tax department, as a service point registered in the documentbanking system 106 may register the FDL (form definition language)representation of a PAN (tax ID) application form in the documentbanking system 106. The FDL representation (or machine-readable formtemplate) of PAN application then may be visible to all document bankingusers such as the account holder 102. It should be appreciated, that theterm “FDL representation” and the “form template” are used throughoutthis disclosure interchangeably without changing its meaning. Further,the application form in this way may be now document banking trustedAuto-fill enabled, i.e. along this form (PAN application form), an“Auto-fill” option may be available for this form to be Auto-filledusing the verified content or information or the pre-stored documents.

The trusted content managing module 324 may be configured to extract orgenerate a number of machine-readable form templates corresponding to anumber of forms stored in the storage repository 302. The forms may beassociated with one or more services provided by the service points 116.Further, the at least one form and the form template is associated withat least one service provided by at least one service point of theservice points 116. Further, structure of the form templates may belearned using one or more known, related art or later developedtechnologies. In an embodiment, the trusted content managing module 324is configured to learn a structure of the form and generate amachine-readable form template corresponding to the form. In anexemplary scenario, the trusted content managing module 324 may generatean XML file that captures all the details about the form. Any suitablelanguage such as, but not limited to, a form definition language (FDL),an XML schema form definition language (FDL), may be used to generatethe form templates and to identify various formats of the variousdocuments from which data is extracted as well as the new forms thatneed to be filled.

FIGS. 7A-7C illustrates exemplary interfaces 700A-700C, respectively,for Auto-filling a form, in accordance with an embodiment of the presentdisclosure. As discussed with reference to FIGS. 1 and 2, the accountholder 102 may select and open a form at the computing device 104. Asshown in interface 700A, a form 702 is opened by the account holder 102.Further, when the form is registered with the document banking system106 or belongs to a service provided by at least one of the registeredservice point 116, then an “Auto-fill” option 704 is also displayedalong with the form. The account holder 102 may opt to auto fill theform by selecting the “Auto-fill” option 704.

When the account holder 102 selects the “Auto-fill” option 704, then asshown on the interface 700B, a window 706 having one or more logincredential fields may be displayed on the computing device 104. Theaccount holder 102 may enter the login credential(s) in the logincredential fields of the window 706. After entering the logincredential(s), the account holder 102 may select a login option 708 asshown in the window 706.

Once the account holder 102 is authenticated by the authenticationmodule 322 of the document banking system 106, the trusted contentmanaging module 324 may fill the form 702 automatically. The interface700C displays a filled form 710 with status information for each of theone or more fields. The status information is shown as markers 712 usingdifferent colors (such as green, red, etc.) and/or symbols (such as ‘√’,‘x’, etc.).

As shown in FIG. 7C, the account holder 102 may interact with individualfield (i.e., Auto-filled field) as per the following rules based on thecontent, as follows:

-   -   (i) The rigid content cannot be changed. If the account holder        102 rejects the rigid content then the whole form fill may be        rejected. The rigid content may be collected as per KYC norms,        and rejecting the rigid content may imply rejection of the        document banking account details of the account holder, which in        turn may result in that document banking system is not being        liable for any other content.    -   (ii) If a verified content is edited by the account holder 102        (or someone else) then the field value is immediately classified        as un-verified.    -   (iii) The un-verified content is editable and the account holder        102 can edit this content as required.    -   (iv) If more than two values are presented for a fields then the        account holder 102 can choose one of them, but the content is        always considered as un-verified content.

In an exemplary scenario, when all the content in the filled form isverified or is rigid content, then the account holder 102 may choose tosubmit the filled form. The trusted content managing module 324 mayexecute the submission of the form according to one or more rulesdefined by a service point of the service points 116. The rules mayinclude transfer of the filled form in a document banking account of theassociated service point or in the storage repository 302. In suchscenario, no back office processing by the service point is required.

In another exemplary scenario, when the content in the filled form ispartially un-verified, then the service point may ask for a few of thewhole set of supporting documents to be attached to have a partial backoffice work at the service point office. In yet another exemplaryscenario, when the content is all un-verified in the filled form, theconsumer or the account holder 102 may still have to dedicate lesseffort or time, while the back office of the service point (116) maystill continue performing its content validation process.

An aspect of the present disclosure allows to auto fill a form usingexisting verified (or un-verified) content from the pre-stored documentsof the account holder.

A further aspect of the present disclosure allows various service pointsto register their form or document template along with customized rulesfor template usage.

Another aspect of the present disclosure performs optical characterrecognition for extracting content from the pre-stored documents.

A yet another aspect of the present disclosure offers secure APIs forthe service points to connect with document banking system and extractuser related information (such as, of the various account holder andservice points) from the storage repository. The storage repository maystore the user related information in form of entity-value pairs.

It will be understood that the modules and the databases referred to inthe previous sections are not necessarily utilized together in a singleconversation analyzing system. Rather, these modules are merelyexemplary of the various modules that may be implemented within aconversation analyzing system. Further, it will be understood that theconversation analyzing module may include more modules than the onesdescribed in this disclosure without departing from the scope of thepresent disclosure.

It will be appreciated that several of the above-disclosed and otherfeatures and functions, or alternatives thereof, may be desirablycombined into many other different systems or applications. Variouspresently unforeseen or unanticipated alternatives, modifications,variations, or improvements therein may be subsequently made by thoseskilled in the art, which are also intended to be encompassed by thefollowing claims.

What is claimed is:
 1. A method for facilitating trusted processing of aplurality of forms for use with a document banking system, comprising:receiving a selection of an Auto-fill option and at least one form froma computing device, wherein an account holder selects the Auto-filloption displayed on the computing device, the at least one formincluding one or more fillable fields; authenticating the account holderbased on at least one login credential entered by the account holder atthe computing device, wherein the account holder has at least onedocument banking account within the document banking system, thedocument banking account including at least one document associated withthe account holder; searching for a form template corresponding to theat least one form in the document banking system, the form templateincluding at least one fillable field similar to the one or morefillable fields of the at least one form; extracting at least one valuecorresponding to the at least one fillable field, the at least one valuebeing extracted from the at least one document associated with theaccount holder; and automatically filling the at least one form byoverlaying the extracted at least one value on the one or more fillablefields of the at least one form, the filled at least one form beingdisplayed along with a status information for each of the one or morefillable fields at the computing device.
 2. The method of claim 1,further comprising identifying the at least one fillable field of theform template which need to be filled.
 3. The method of claim 2, furthercomprising generating and storing a plurality of form templatescorresponding to the plurality of forms associated with one or moreservices, wherein the one or more services are provided by the pluralityof service points.
 4. The method of claim 3, wherein the documentbanking system maintains a plurality of document banking accountsassociated with at least one of a plurality of account holders and aplurality of service points, further wherein each of the plurality ofdocument banking accounts stores a plurality of documents that areverified by a plurality of verification partners.
 5. The method of claim4, wherein the form template and the at least one form are associatedwith at least one service provided by a service point of the pluralityof service points, wherein the service point is registered with thedocument banking system and has at least one document banking account inthe document banking system.
 6. The method of claim 5, furthercomprising transferring the filled at least one form in the at least onedocument banking account of the service point based on one or more rulesdefined by the service point, wherein the filled at least one form istransferred when the account holder provides submit instruction at thecomputing device.
 7. The method of claim 6, wherein the statusinformation is at least one of rigid, verified, and un-verified.
 8. Themethod of claim 7, further comprising allowing the account holder tointeract with the displayed filled at least one form, wherein theaccount holder is allowed to reject or select the at least one value ofeach of the one or more fillable fields.
 9. The method of claim 8,further comprising rejecting the filled at least one form when theaccount holder rejects at least one of the one or more fillable fieldshaving an associated status information as rigid.
 10. The method ofclaim 8, further comprising displaying, to the account holder, one ormore values for the at least one of the one or more fillable fields whenthe one or more values are available in the document banking system forthe at least one of the one or more fillable fields.
 11. A documentbanking system for facilitating trusted processing of a plurality offorms, the document banking system comprising: a storage repositoryconfigured to store a plurality of documents associated with a pluralityof document banking accounts, wherein each of the plurality of documentbanking accounts is associated with at least one of a plurality ofaccount holders and a plurality of service points, a plurality ofverification partners verifying the plurality of documents; atransceiving module configured to receive a selection of an Auto-filloption and at least one form from a computing device, wherein an accountholder selects the Auto-fill option displayed on the computing device,the at least one form including one or more fillable fields; anauthentication module configured to authenticate the account holderbased on at least one login credential entered by the account holder atthe computing device, the account holder having at least one documentbanking account in the document banking system, the document bankingaccount including at least one document associated with the accountholder; and a trusted content managing module configured to: search fora form template corresponding to the at least one form in the storagerepository, wherein the form template comprises at least one fillablefield similar to the one or more fillable fields of the at least oneform; identify the at least one fillable field of the form templatewhich need to be filled; extract at least one value corresponding to theat least one fillable field, wherein the at least one value is extractedfrom the at least one document associated with the account holder; andautomatically fill the at least one form by overlaying the extracted atleast one value onto the one or more fillable fields of the at least oneform.
 12. The document banking system of claim 11, further comprising adisplay module configured to: display the at least one form and the“Auto-fill” option on the computing device; and display the filled atleast one form along with the status information for each of the one ormore fillable fields on the computing device, wherein the account holderis allowed to interact with the filled at least one form.
 13. Thedocument banking system of claim 12, wherein the trusted contentmanaging module is further configured to generate and store a pluralityof form templates corresponding to the plurality of forms associatedwith one or more services, the one or more service being provided by theplurality of service points.
 14. The document banking system of claim13, wherein the form template and the at least one form are associatedwith at least one service provided by a service point of the pluralityof service points, wherein the service point is registered with thedocument banking system and has at least one document banking account inthe document banking system.
 15. The document banking system of claim14, wherein the trusted content managing module is further configured totransfer the filled at least one form and one or more supportingdocuments in the at least one document banking account of the servicepoint based on a pre-defined one or more rules, further wherein thefilled at least one form is transferred when the account holder providessubmit instruction at the computing device.
 16. The document bankingsystem of claim 15, wherein the status information is at least one of arigid, verified, and un-verified.
 17. The document banking system ofclaim 16, wherein the display module is configured to provide aninterface at the computing device to allow the account holder tointeract with the filled at least one form, the account holder beingallowed to reject or select the at least one value of each of the one ormore fillable fields.
 18. The document banking system of claim 17,wherein the display module is further configured to display, to theaccount holder, one or more values for the at least one of the one ormore fillable fields if the one or more values are available in thestorage repository for the at least one of the one or more fillablefields.
 19. The document banking system of claim 18, wherein the trustedcontent managing module is further configured to reject the filled atleast one form when the account holder rejects at least one of the oneor more fillable fields having an associated status information asrigid.
 20. A method for facilitating trusted processing of a pluralityof forms for use with a document banking system, the method comprising:receiving a selection of an “Auto-fill” option and at least one formfrom a computing device, wherein an account holder selects the“Auto-fill” option displayed on the computing device, the at least oneform including one or more fillable fields; authenticating the accountholder based on at least one login credential entered by the accountholder at the computing device, wherein the account holder has at leastone document banking account in the document banking system, thedocument banking account including at least one document associated withthe account holder; searching for a form template corresponding to theat least one form in the document banking system, the form templateincluding at least one fillable field similar to the one or morefillable fields of the at least one form; identifying the at least onefillable field of the form template which needs to be filled; extractingat least one value corresponding to the at least one fillable field,wherein the at least one value is extracted from the at least onedocument of the account holder, the at least one document being verifiedby at least one verification partner; automatically filling the at leastone form by overlaying the extracted at least one value on the one ormore fillable fields of the at least one form, wherein the filled atleast one form is displayed along with a status information for each foreach of the one or more fillable fields at the computing device, thestatus information being at least one of a rigid, verified, andun-verified; and allowing the account holder to interact with the filledat least one form displayed at the computing device.
 21. A documentbanking system for facilitating trusted processing of a plurality offorms, the document banking system comprising: a storage repositoryconfigured to store a plurality of documents associated with a pluralityof document banking accounts, wherein the plurality of document bankingaccounts are associated with a plurality of account holders and aplurality of service points, the plurality of documents being verifiedby a plurality of verification partners; a transceiving moduleconfigured to receive a selection of an Auto-fill option and at leastone form from a computing device, wherein an account holder selects theAuto-fill option displayed on the computing device, the at least oneform including one or more fillable fields; an authentication moduleconfigured to authenticate the account holder based on at least onelogin credential entered by the account holder at the computing device,the account holder having at least one document banking account in thedocument banking system, the document banking system including at leastone document associated with the account holder; and a trusted contentmanaging module configured to: search for a form template correspondingto the at least one form in the storage repository, wherein the formtemplate includes at least one fillable field similar to the one or morefillable fields of the at least one form; identify the at least onefillable field of the form template which need to be filled; extract atleast one value corresponding to the at least one fillable field,wherein the at least one value is extracted from the at least onedocument associated with the account holder; and fill the form templateby overlaying the extracted at least one value on the one or morefillable fields of the at least one form, wherein the filled at leastone form is displayed along with a status information for each of theone or more fillable fields at the computing device, the statusinformation being at least one of a rigid, verified, and un-verified.